Everything about Write-read Conflict totally explained
In
computer science, in the field of
databases,
Write-Read Conflict, also known as
reading uncommitted data, is a computational anomaly associated with interleaved execution of transactions.
Given a schedule D
»
T2 could read a database object A, modified by T1 which hasn't committed. This is a
dirty read.
T1 may write some value into A which makes the database inconsistent. It is possible that interleaved execution can expose this inconsistency and lead to inconsistent final database state, violating
ACID rules.
Strict 2PL overcomes this inconsistency by locking T2 out from performing a Read/Write on A. Note however that
Strict 2PL can have a number of drawbacks, such as the possibility of
deadlocks.
Further Information
Get more info on 'Write-read Conflict'.
|
External Link Exchanges
Do you know how hard it is to get a link from a large encyclopaedia? Well we're different and will prove it. To get a link from us just add the following HTML to your site on a relevant page:
<a href="http://write-read_conflict.totallyexplained.com">Write-Read conflict Totally Explained</a>
Then simply click through this link from your web page. Our crawlers will verify your link, extract the title of your web page and instantly add a link back to it. If you like you can remove the words Totally Explained and embed the link in article text.
As long as your link remains in place, we'll keep our link to you right here. Please play fair - our crawlers are watching. Your site must be closely related to this one's topic. Any kind of spamming, dubious practises or removing the link will result in your link from us being dropped and, potentially, your whole site being banned. |
